@bondydaa @mananjadhav One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@marktoman Quick bump on @bondydaa's comment to fill out the checklist and update the screenshots for all platforms.

On iOS, when entering:

```
Test
```

the converted result (commentText here) is <pre>Test<br /></pre>, which is correct and the same for other platforms.

Editing works as expected:

But, it is rendered like this:

So I'm not sure if I should try to change how it is rendered somehow.

Hmm that's strange, it only happens on iOS (native or mWeb?) that it's still rendered with the extra new line?

Only native, Safari works the same as desktop. I'll dig into the rendering.

Apparently, the HTML standard renders the lines the way we settled on (the web/desktop videos), but this behavior is behind a flag on native:

Recommended value is true on non-web platforms.
https://meliorence.github.io/react-native-render-html/api/renderhtmlprops#enableexperimentalbrcollapsing

I've tested it by adding props.sharedProps.enableExperimentalBRCollapsing = true; here and it solves the problem, i.e., it makes the lines consistent between web and native (both ios and android).

Hmm the other half of that recommendation is slightly concerning

Also note that this is an experimental feature, thus subject to behavioral instability.

but I think you're right that's what we want to provide consistent behavior across all platforms.

Go ahead and commit that change then and we can go from there.

I've merged new changes and tested it everywhere, and it works as expected.

Just checking if I haven't accidentally removed something in the issue description, the PR reviewer checklist will be added by a reviewer, correct?

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
• I checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified tests pass on all platforms & I tested again on:
  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified proper code patterns were followed (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Just checking if I haven't accidentally removed something in the issue description, the PR reviewer checklist will be added by a reviewer, correct?

Thanks for the PR and the thorough updates @marktoman. I've reviewed the PR and completed the checklist. All good here @bondydaa.

Can somebody please explain the process? Does this wait for somebody to assign an internal engineer?

Waiting on @bondydaa to validate the checklist and merge the PR. Quick bump here @bondydaa

sorry was OOO on Friday, taking a look.

Performance Comparison Report 📊

Significant Changes To Duration

There are no entries

Meaningless Changes To Duration

🚀 Deployed to staging by https://github.com/bondydaa in version: 1.2.75-0 🚀

🚀 Deployed to production by https://github.com/melvin-bot[bot] in version: 1.2.75-0 🚀